compiletest: Support revisions in debuginfo (read: debugger) tests #150201
+43
−29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
And start using revisions in
tests/debuginfo/macro-stepping.rsto prevent regressing both with and withoutSingleUseConstsMIR pass.I recommend commit-by-commit review.
TODO
LineNonewtype to avoid+1magic here and there #150205 once merged so we don't have to add another "+ 1".CC
CC @Zalathar since you might have opinions about that I expose a helper function to reduce duplication
CC @saethlin since this is what we will use for
tests/debuginfo/basic-stepping.rsin #147426 (in the same way I use it intests/debuginfo/macro-stepping.rshere)